fix: Enhance content_to_json for backward compatibility#374
Merged
Conversation
- Modified content_to_json function to handle non-JSON content - Introduced _try_remove_markdown_block_flag to preprocess content - Ensured backward compatibility with older devchat-api versions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR includes modifications to the
content_to_jsonfunction that allow it to handle non-JSON content gracefully. A helper function_try_remove_markdown_block_flaghas been introduced to preprocess content for compatibility with older versions of the devchat-api.